Usage Archiving

Every time a subscription A billing entity that incurs a charge. Examples include a network attached device whose usage you want to measure and charge for, or a monthly software subscription uses their handset A mobile phone to make a call, send a text or browse the web, the network In the context of CMP, the infrastructure on which usage of registered customers will be measured – this could be a mobile phone network, broadband network or other non-telecommunications network. records this activity and makes the information available for collection, typically in batches. CMP Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. receives many rated usage The consumption of services, for example a subscriber using call minutes. batches every day and over time the database can contain a large volume of usage records.

The Usage Archiving job creates a new rated usage archive and transfers newly invoiced usage into that archive, thus separating billed and unbilled usage. This helps to speed up access to unbilled usage during important processes such as invoicing. It also facilitates purging out-of-date billed usage data from the system. The job looks in the Invoice Header table based on the Invoice Run Number, which tells it which invoices were produced during the Invoice Production run. Based on these invoices, the usage can be determined from the Call Detail table, which holds usage for each invoice. Once the Call Detail table is archived, the Usage Extension, Usage Attribute, Usage Attribute Unique and CPP Calls Basket tables can then also be archived, based off the archived Call Detail table. A header record is created in the CM Archive Header table per Usage Archiving run, and records for each table that was archived in the run is created in the CM Archive Detail table.

This job is part of the scheduled Billing process which coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.

The following Billing jobs must be run in sequence:

Invoice Production job
Statement Production job
Bill Print job
Invoice Posting job
Usage Archiving

The jobs must run in this sequence because there are dependencies between the various jobs. For example, the Statement Production job relies on the invoices produced by Invoice Production job.

Relevant JSON JavaScript Object Notation. JSON is a lightweight format for storing and transporting data, often used when data is sent from a server to a web page. schema:

Not applicable. This job does not consume any external feed from a third party Of software; a reusable component developed to be either freely distributed or sold by an entity other than the original vendor of the development platform. nor does it produce a feed for a third party; it operates on CMP tables.